<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><title>Minutes of Meeting(Development Team)</title>
  
                           
  <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
               
  <meta name="author" content="Barry Radloff"></head>

<body>
       
<h1 style="text-align: center;">Minutes of Meetings</h1>
       
<h1 style="text-align: center;">Velocityme 13 </h1>
    <br>
       
<table cellpadding="2" cellspacing="2" border="1" style="text-align: left; width: 100%;">
      <tbody>
        <tr>
          <th valign="top" bgcolor="#99ffff">Date<br>
          </th>
          <th valign="top" bgcolor="#99ffff">Time<br>
          </th>
          <th valign="top" bgcolor="#99ffff">Venue<br>
        </th>
        <th valign="top" bgcolor="#99ffff">Attendants<br>
          </th>
          <th valign="top" bgcolor="#99ffff">Apologies<br>
          </th>
        </tr>
        <tr>
          <td valign="top">2002/11/19<br>
          </td>
          <td valign="top">19:50<br>
          </td>
          <td valign="top">22 Bordeaux, Tokai<br>
        </td>
        <td valign="top">Robert Crida(RC)<br>
    Barry Radloff(BR)<br>
        Wayne Paverd(WP)<br>
          </td>
          <td valign="top">David Spencers(DS)<br>
          </td>
        </tr>
               
  </tbody>    
</table>
    <br>
       
<table cellpadding="2" cellspacing="2" border="1" style="text-align: left; width: 100%;">
      <tbody>
        <tr>
          <th valign="top" bgcolor="#99ffff">Description<br>
          </th>
          <th valign="top" bgcolor="#99ffff">Responsibility<br>
          </th>
          <th valign="top" bgcolor="#99ffff">Due date<br>
          </th>
        </tr>
        <tr>
          <td valign="top">1. Minutes of meeting 12 were approved<br>
          </td>
          <td valign="top"><br>
          </td>
          <td valign="top"><br>
          </td>
        </tr>
     <tr>
       <td valign="top">2. General<br>
       </td>
       <td valign="top"><br>
       </td>
       <td valign="top"><br>
       </td>
     </tr>
     <tr>
      <td valign="top">2.1. BR Noted that JRUN was not infact an EJB container,
but a servlet and jsp container<br>
      </td>
      <td valign="top"><br>
      </td>
      <td valign="top"><br>
      </td>
    </tr>
    <tr>
       <td valign="top">3. Discussion of work done<br>
       </td>
       <td valign="top"><br>
       </td>
       <td valign="top"><br>
       </td>
     </tr>
     <tr>
      <td valign="top">3.1. Templates<br>
      </td>
      <td valign="top"><br>
      </td>
      <td valign="top"><br>
      </td>
    </tr>
    <tr>
       <td valign="top">3.1.1. RC suggested that the library idea was scrapped
and the templates should be orginized from the root of the tree<br>
      </td>
       <td valign="top"><br>
       </td>
       <td valign="top"><br>
       </td>
     </tr>
     <tr>
       <td valign="top">3.1.2. It was agreed by all that the same idea as
libraries be used, but implemented as tree nodes to organise the templates.<br>
      </td>
      <td valign="top"><br>
      </td>
      <td valign="top"><br>
      </td>
    </tr>
    <tr>
      <td valign="top">3.1.3 WP noted that there may be a problem when sharing
templates between tree nodes, such as versions, and will each node get its
own copy of the template or just a like of some kind<br>
      </td>
      <td valign="top"><br>
      </td>
      <td valign="top"><br>
      </td>
    </tr>
    <tr>
      <td valign="top">3.1.4. It was agreed that templates were infact a
nice to have and not critical to version 1 (one)<br>
      </td>
      <td valign="top"><br>
      </td>
      <td valign="top"><br>
      </td>
    </tr>
    <tr>
      <td valign="top">3.2 Roles, A question was raised as to deletion of
roles. &nbsp;Instead of deleting fagging was noted as a better option. &nbsp;It
was decided that this discussion applied to most area's where deletion was
an issue.<br>
      </td>
      <td valign="top"><br>
      </td>
      <td valign="top"><br>
      </td>
    </tr>
    <tr>
      <td valign="top">3.3. Setup of task state machines was added by RC.
&nbsp;WP suggested that no edit functionality should be necessary for version
1 (one)<br>
      </td>
      <td valign="top"><br>
      </td>
      <td valign="top"><br>
      </td>
    </tr>
    <tr>
      <td valign="top">3.4. Concurrent Editing<br>
      </td>
      <td valign="top"><br>
      </td>
      <td valign="top"><br>
      </td>
    </tr>
    <tr>
      <td valign="top">3.4.1. WP raised the issue of concurrent editting<br>
      </td>
      <td valign="top"><br>
      </td>
      <td valign="top"><br>
      </td>
    </tr>
    <tr>
      <td valign="top">3.4.2. It was agreed that a request will need to be
made to edit a tree node of sorts, this should be a timed locked and after
a period of inactivity the lock will be released.<br>
If the user still wants to make changes and the lock has been lost then the
system must determine if it is in the best interests of the data to allow
an immediate lock to change the data. &nbsp;e.g. If another user has in the
mean time changed a field the system must reject the lock or possibly prompt
the user if he/she wishes to view the changed fields before updating the
record. &nbsp;The user can optionally choose to renew their lock and refresh
their data, make the changes and save the new changes. &nbsp;This subject
will be discussed in more detail at a later stage, but this is the basis
for the locking mechanism<br>
      </td>
      <td valign="top"><br>
      </td>
      <td valign="top"><br>
      </td>
    </tr>
    <tr>
      <td valign="top">3.5. User Interface<br>
      </td>
      <td valign="top"><br>
      </td>
      <td valign="top"><br>
      </td>
    </tr>
    <tr>
      <td valign="top">3.5.1. It was decided that there are many ways to
implement the interface, and the implementation boilt down to preferences<br>
      </td>
      <td valign="top"><br>
      </td>
      <td valign="top"><br>
      </td>
    </tr>
    <tr>
      <td valign="top">3.5.2. &nbsp;It was decided that the interface would
consist of a navigatable tree on the left/right and the pertinent information
about the tree node on the right/left.(configurable?)<br>
      </td>
      <td valign="top"><br>
      </td>
      <td valign="top"><br>
      </td>
    </tr>
    <tr>
      <td valign="top">3.5.3. All the nodes in the tree view would have the
potential to be viewed as the root.<br>
      </td>
      <td valign="top"><br>
      </td>
      <td valign="top"><br>
      </td>
    </tr>
    <tr>
      <td valign="top">3.5.4. There will be an easy access toolbar/shortcut
bar<br>
      </td>
      <td valign="top"><br>
      </td>
      <td valign="top"><br>
      </td>
    </tr>
    <tr>
      <td valign="top">3.5.5. there will need to to be a button to navigate
to the parent of the current root if it is applicable<br>
      </td>
      <td valign="top"><br>
      </td>
      <td valign="top"><br>
      </td>
    </tr>
    <tr>
      <td valign="top">3.5.6. &nbsp;There will be a mock up made by RC if
there is time to do it<br>
      </td>
      <td valign="top"><br>
      </td>
      <td valign="top"><br>
      </td>
    </tr>
    <tr>
      <td valign="top">3.4. Gantt charts require some more thought and will
be dicussed later<br>
      </td>
      <td valign="top"><br>
      </td>
      <td valign="top"><br>
      </td>
    </tr>
    <tr>
      <td valign="top">3.5. BR was reminded that the dependants and dependancies
made up the Gantt chart flow.<br>
      </td>
      <td valign="top"><br>
      </td>
      <td valign="top"><br>
      </td>
    </tr>
    <tr>
      <td valign="top">3.6. Tree issues arose about the tree node response
time and loading of data, this will be decided on at implementation time
to determine the best response. &nbsp;Possibly only one or two levels will
be loaded at a time.<br>
      </td>
      <td valign="top"><br>
      </td>
      <td valign="top"><br>
      </td>
    </tr>
    <tr>
      <td valign="top">4. Actions<br>
      </td>
      <td valign="top"><br>
      </td>
      <td valign="top"><br>
      </td>
    </tr>
    <tr>
      <td valign="top">4.1. BR and RC would continue with the use case descriptions.<br>
      </td>
      <td valign="top"><br>
      </td>
      <td valign="top"><br>
      </td>
    </tr>
  </tbody>
</table>
<br>
       
<table cellpadding="2" cellspacing="2" border="1" style="text-align: left; width: 100%;">
      <tbody>
        <tr>
          <th valign="top" style="background-color: rgb(153, 255, 255);" bgcolor="#99ffff">Author</th>
        <th valign="top" bgcolor="#99ffff">Date<br>
          </th>
          <th valign="top" bgcolor="#99ffff">Next Venue<br>
         </th>
                 <th valign="top" bgcolor="#99ffff">Next Meeting<br>
          </th>
        </tr>
             <tr>
         <td valign="top">Barry Radloff<br>
         </td>
         <td valign="top">2002/11/21<br>
         </td>
         <td valign="top">13 Pearson Road, Tableview<br>
         </td>
                <td valign="top">2002/11/26<br>
         </td>
       </tr>
               
  </tbody>    
</table>
    <br>
    <br>
   <br>
  <br>
 <br>
</body></html>